[PR #8216/a5b2b5ce backport][stable-8] Add support for docker-v2 protocol in Keycloak modules #8239
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #8216 as merged into main (a5b2b5c).
SUMMARY
This pull request introduces the addition of the "docker-v2" protocol support to the
keycloak_client
,keycloak_clientscope
, andkeycloak_clienttemplate
modules within the community.general collection. The "docker-v2" protocol is a valid and supported option in Keycloak, which is crucial for configurations involving Docker registry authentication, among others. Fixes #8215.ISSUE TYPE
COMPONENT NAME
keycloak_client
keycloak_clientscope
keycloak_clienttemplate
ADDITIONAL INFORMATION
I have enhanced the
protocol
parameter across thekeycloak_client
,keycloak_clientscope
, andkeycloak_clienttemplate
modules to include the "docker-v2" option. It's important to note that the existing protocol choices varied across different modules — some were limited to['openid-connect', 'saml']
, while others used Python constants to define the choices. I've respected the existing structure and conventions in each module, only extending them to include "docker-v2".For instance, if a module's protocol choices were previously defined as:
I have updated this to
And similarly, for modules using Python constants to define protocol choices, I've appended "docker-v2" to the existing list without altering the existing structure.
The documentation for each affected module has been updated to include "docker-v2" as a valid protocol option.
The modifications were tested to confirm that the "docker-v2" protocol is recognized and behaves as expected across the updated modules. I encourage further testing by the community to validate these changes across various usage scenarios.
I have not verified the potential error message from the Keycloak API when this option is used when the keycloak server has not activated the docker-v2 protocol, (disabled by default and enabled by running
bin/standalone.sh|bat -Dkeycloak.profile.feature.docker=enabled
starting the service, see (https://www.keycloak.org/server/features).